Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1285

reference
388-tree-1
name
1285
tree-preservation-order

undefined

388-tpo-1
uprn
address-text
point
POINT (-1.025657 50.883887)
geometry
MULTIPOLYGON (((-1.025586 50.883880,-1.025589 50.883893,-1.025599 50.883906,-1.025614 50.883916,-1.025634 50.883923,-1.025656 50.883925,-1.025678 50.883923,-1.025698 50.883917,-1.025714 50.883907,-1.025724 50.883895,-1.025728 50.883881,-1.025725 50.883867,-1.025715 50.883854,-1.025699 50.883844,-1.025680 50.883838,-1.025658 50.883835,-1.025636 50.883837,-1.025616 50.883843,-1.025600 50.883853,-1.025589 50.883866,-1.025586 50.883880)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL